Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
normalize-exception
Advanced tools
Normalize:
Error
instancesname
, message
, stack
, constructor
) that are
missing, invalid,
enumerable, readonly,
non-writable,
non-configurable,
non-extensible, proxied or
throwingerror.cause
and
error.errors
recursively, when presentimport normalizeException from 'normalize-exception'
try {
throw 'message'
} catch (error) {
console.log(error) // 'message'
console.log(normalizeException(error)) // Error: message
console.log(normalizeException(error) instanceof Error) // true
}
npm install normalize-exception
This package works in both Node.js >=14.18.0 and
browsers.
It is an ES module and must be loaded using
an import
or import()
statement,
not require()
.
error
any
options
Options
Return value: Error
normalizeException()
never throws.
If error
is an Error
instance, it is returned. Any missing or invalid error
property is directly modified.
If it is not an Error
instance, a new one is created and returned.
Options are an optional object with the following properties.
Type: boolean
Default: false
Unless true
,
error.cause
and
error.errors
are normalized recursively, when present.
try {
throw 'message'
} catch (error) {
console.log(error) // 'message'
console.log(normalizeException(error)) // Error: message
console.log(normalizeException(error) instanceof Error) // true
}
try {
throw { name: 'TypeError', message: 'message' }
} catch (error) {
console.log(normalizeException(error)) // TypeError: message
}
try {
throw null
} catch (error) {
console.log(error.message) // Throws
console.log(normalizeException(error).message) // 'null'
}
try {
const error = new TypeError('message')
error.name = undefined
throw error
} catch (error) {
console.log(error.name) // undefined
console.log(normalizeException(error).name) // 'TypeError'
}
try {
const error = new TypeError('message')
error.constructor = RangeError
throw error
} catch (error) {
console.log(error.constructor) // RangeError
console.log(normalizeException(error).constructor) // TypeError
}
try {
const error = new Error('message')
error.stack = undefined
throw error
} catch (error) {
console.log(error.stack) // undefined
console.log(normalizeException(error).stack) // 'Error: message ...'
}
try {
const error = new Error('message')
error.message = true
throw error
} catch (error) {
console.log(typeof error.message) // 'boolean'
console.log(typeof normalizeException(error).message) // 'string'
}
class ExampleError extends Error {
constructor(...args) {
super(...args)
// Common mistake: this makes `error.name` enumerable
this.name = 'ExampleError'
}
}
try {
throw new ExampleError('message')
} catch (error) {
console.log({ ...error }) // { name: 'ExampleError' }
console.log({ ...normalizeException(error) }) // {}
}
try {
const error = new Error('message')
Object.defineProperty(error, 'message', { get: () => 'message' })
throw error
} catch (error) {
error.message = 'other' // Throws
normalizeException(error).message = 'other' // Does not throw
}
try {
const error = new Error('message')
Object.defineProperty(error, 'message', { value: '', writable: false })
throw error
} catch (error) {
error.message = 'other' // Throws
normalizeException(error).message = 'other' // Does not throw
}
try {
const error = new Error('message')
Object.defineProperty(error, 'message', { value: '', configurable: false })
throw error
} catch (error) {
delete error.message // Throws
delete normalizeException(error).message // Does not throw
}
try {
const error = new Error('message')
Object.preventExtensions(error)
throw error
} catch (error) {
error.prop = true // Throws
normalizeException(error).prop = true // Does not throw
}
try {
throw new Proxy(new Error('message'), {})
} catch (error) {
const { toString } = Object.prototype
console.log(toString.call(error)) // '[object Object]'
console.log(toString.call(normalizeException(error))) // '[object Error]'
}
try {
throw new Proxy(new Error('message'), {
get() {
throw new Error('example')
},
})
} catch (error) {
console.log(error.message) // Throws
console.log(normalizeException(error).message) // Does not throw
}
try {
const error = new Error('message')
Object.defineProperty(error, 'message', {
get() {
throw new Error('example')
},
})
throw error
} catch (error) {
console.log(error.message) // Throws
console.log(normalizeException(error).message) // Does not throw
}
error.cause
try {
throw new Error('message', { cause: 'innerError' })
} catch (error) {
console.log(error.cause instanceof Error) // false
console.log(normalizeException(error).cause instanceof Error) // true
}
error.errors
try {
throw new AggregateError(['innerError'], 'message')
} catch (error) {
console.log(error.errors[0] instanceof Error) // false
console.log(normalizeException(error).errors[0] instanceof Error) // true
}
modern-errors
: Handle errors
like it's 2022 🔮error-custom-class
: Create
one error classerror-class-utils
: Utilities
to properly create error classeserror-serializer
: Convert
errors to/from plain objectsmerge-error-cause
: Merge an
error with its cause
is-error-instance
: Check if
a value is an Error
instanceset-error-class
: Properly
update an error's classset-error-message
: Properly
update an error's messageset-error-props
: Properly
update an error's propertieserror-cause-polyfill
:
Polyfill error.cause
handle-cli-error
: 💣 Error
handler for CLI applications 💥log-process-errors
: Show
some ❤ to Node.js process errorsFor any question, don't hesitate to submit an issue on GitHub.
Everyone is welcome regardless of personal background. We enforce a Code of conduct in order to promote a positive and inclusive environment.
This project was made with ❤️. The simplest way to give back is by starring and sharing it online.
If the documentation is unclear or has a typo, please click on the page's Edit
button (pencil icon) and suggest a correction.
If you would like to help us fix a bug or add a new feature, please check our guidelines. Pull requests are welcome!
2.11.0
FAQs
Normalize exceptions/errors
We found that normalize-exception demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.